Skip to content

[AutoPR- Security] Patch fluent-bit for CVE-2026-58055 [MEDIUM]#17883

Open
azurelinux-security wants to merge 2 commits into
microsoft:3.0-devfrom
azurelinux-security:azure-autosec/fluent-bit/3.0/1150963
Open

[AutoPR- Security] Patch fluent-bit for CVE-2026-58055 [MEDIUM]#17883
azurelinux-security wants to merge 2 commits into
microsoft:3.0-devfrom
azurelinux-security:azure-autosec/fluent-bit/3.0/1150963

Conversation

@azurelinux-security

@azurelinux-security azurelinux-security commented Jul 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Auto Patch fluent-bit for CVE-2026-58055.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1150963&view=results

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge
Summary

What does the PR accomplish, why was it needed?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • N/A
Links to CVEs
Test Methodology

@microsoft-github-policy-service microsoft-github-policy-service Bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Jul 1, 2026
@BinduSri-6522866

BinduSri-6522866 commented Jul 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Patch is backported manually to support the existing codebase.

@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review July 2, 2026 11:21
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner July 2, 2026 11:21
Kanishk-Bansal
Kanishk-Bansal requested changes Jul 3, 2026
View reviewed changes

@Kanishk-Bansal Kanishk-Bansal left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please check are we even shipping nghttpx

as acc to me

Top-level CMakeLists.txt sets ENABLE_LIB_ONLY ON

lib/nghttp2/CMakeLists.txt: ENABLE_LIB_ONLY ⇒ ENABLE_APP OFF

lib/nghttp2/src/CMakeLists.txt: all shrpx_* sources are gated behind if(ENABLE_APP)

➡️ The patched files are never compiled into fluent-bit. This is a functional no-op — fluent-bit is effectively not affected.

@BinduSri-6522866

BinduSri-6522866 commented Jul 3, 2026 •
edited
Loading

Copy link
Copy Markdown

As per ldd output, it shows /usr/bin/fluent-bit is dynamically linked to the system library libnghttp2.so.14 at /usr/lib/libnghttp2.so.14.
image

During build/runtime, it is not statically using nghttp2 code for linkage path. It might be dynamically links to system libnghttp and not the nghttp2 in fluent-bit package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Kanishk-Bansal Kanishk-Bansal Kanishk-Bansal requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

3.0-dev PRs Destined for AzureLinux 3.0 AI Backport AutoPR-Security Packaging security

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@azurelinux-security @BinduSri-6522866 @Kanishk-Bansal